home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94a.txt
/
000001_icon-group-sender _Fri Jan 7 13:29:34 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-08-19
|
1KB
Received: by cheltenham.cs.arizona.edu; Sun, 9 Jan 1994 19:06:01 MST
Date: 7 Jan 94 13:29:34 GMT
From: agate!howland.reston.ans.net!pipex!pipex!not-for-mail@ucbvax.Berkeley.EDU (Ian Phillipps)
Organization: PIPEX Ltd, Cambridge, UK.
Subject: Re: Icon and sockets
Message-Id: <2gjo3u$213@tank.pipex.net>
References: <CJ8CLp.EqF@walter.bellcore.com>
Sender: icon-group-request@cs.arizona.edu
To: icon-group@cs.arizona.edu
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
In article <CJ8CLp.EqF@walter.bellcore.com>,
>Actually, what I wanted was to manage several sockets simultaneously,
>handling connects and disconnects dynamically. I chose to go with a C
>process that managed the sockets and wrote to a file which I just poled.
>Any better ideas?
Not sure if I'm allowed to say this here :-) but that sounds like more of a
job for Perl, if you want the flexibility of a high-level interpreted
language. Horses for courses, and all that....
[See comp.lang.perl - versions for Unix + other systems from various FTP sites]
Ian